Cream of the Crop 20/Cream of the Crop 20 (Terry Blount) (1996).iso/os2/gigo0714.zip/DIGEST.DOC

Text File | 1995-08-27 | 6KB | 161 lines

Area : Jason's Netmail

Date : Thu Aug 17, 21:46                                               pvt rcv
From : [e-mail]                                      1:203/2
To   : Jason Fesler                                           1:203/7707
Subj : Digest doc's
────────────────────────────────────────────────────────────────────────────────

@INTL 1:203/7707 1:203/2
@MSGID: [e-mail] 38590001
@PID GIGO+ sn 1 at gigo vsn 0.99.950801

Hello [e-mail]!


Gigo Digest Processor Documentation v. 950801

This software is for Digest versions of your mailing-lists.
A Digest is a series of individual mailing-list messages packaged
up into one message (so you may for instance get 10 mailing-list
messages sent as one email.)

1) System Requirements:
A working copy of GIGO.
A list-server (see the one that came with GIGO)
A working knowledge of mailing-lists and how GIGO utilizes them in
particular)

2) Installation:

For each mailing-list you wish to have a Digest for, you must place
a copy of digest.cfg in the directory where the .MLQ files for that
list are stored.

Sample digest.cfg:
------------------
GIGO
From gigo-owner %s remote from gigo.com
Received: gigo.com (digest proc); %s
Date: %s
From: [e-mail]
Reply-To: [e-mail]
To: [e-mail]

Administrative note:

This is the GIGO support mailing list, in digest format.  To unsubscribe,
send a message to "[e-mail]", message body
"unsub digest".

Please remember that when you post, people all over the world will be reading.
The official language is English to help make sure as many people can
participate
as possible.
------------------
Explanation of digest.cfg line-by-line:
Line 1: Name of the associated mailing-list (ie if you have widg-d.ml for the
digest and widget.ml for the mailing-list, the first line would be WIDGET.
Line 2-7: Must exist in the specified order (%s's mandatory), but
you should change the value's to what they need to be such as
"Received: widget.widget.com (digest proc); %s"
if you were widget.widget.com.
Line 8+: This will be prepended to all digest messages, so you may want
to state what digest this is, how people can unsubscribe etc..

Sample maillist.cfg

CAPTURE gigo\ gigo-l [e-mail] - GIGO badmail.ml GIGO Support
CAPTURE gigo\ digest [e-mail] - GIGO badmail.ml GIGO Support

EXPLODE gigo\ gigo.ml   [e-mail] - [e-mail]
EXPLODE digest\ digest.ml [e-mail] - -

The CAPTURE line for the digest should point to the same directory as
the mailing list (this is so that if someone replies to the digest message
the people on the mailing-list will see it).
The EXPLODE line however should point to a directory specific to the digest
itself. The digest should also have it's own .ml and .faq.

3) Subscribing to a digest:

A person subscribes to a digest in the same method as they would a normal
mailing-list (as the digest uses the standard .ml file produced by the
listserver software) except they would subscribe to widg-d instead of widg
(assuming you had widg.ml for the Widget Mailing list and widg-d.ml for the
Widget Mailing list (Digest).

4) Operation:
However often you wish to have a Digest produced (once a day is recommended)
you should have an event which calls DIGESTP.EXE (or DIGEST.EXE for DOS
people) from inside the associated mailing-list directory for a digest.
This will create a bunch of *.DLQ files (Digest Queue files.) These
should then be moved to the directory pointed to by the EXPLODE statement
for the digest (but they should be renamed to *.MLQ (so GATEWAY.EXE can
process them.)) This should be repeated for each digest you have.
NOTE: Make sure you set the MAILSERVER environment variable before calling
DIGEST.EXE if you are operation TCP/IP instead of UUCP (UUCP people should
not set this variable.)

Sample .cmd/.bat
----------------
rem process digest wsomr-l

cdd n:\gateway\wsomr-l

rem set MAILSERVER so that digestp realizes we are TCP/IP
set mailserver=mail.calweb.com
n:\gateway\digestp
move *.dlq n:\gateway\wsomr-d\*.mlq

rem process digest changi
cdd e:\gateway\changi

rem set MAILSERVER so that digestp realizes we are TCP/IP
set mailserver=mail.calweb.com
n:\gateway\digestp
move *.dlq e:\gateway\changi-d\*.mlq
----------------

That's it, if you need furthur assistance please contact:
[e-mail]

This Documentation was written by Stephen Griffin ([e-mail])
and Jason takes no responsibility for typing errors, grammatical foul-ups
and other minor mistakes.
(c) Copyright 1995 Jason Fesler

Stephen

--- GoldED 2.41
--
Stephen Griffin -Sysop/Sysadmin bdragon.jjm.com f401.n333.z1.fidonet.org
Stephen Griffin 1:333/401

--- Email headers follow ---
Apparently-to: [e-mail]
X-Delivered-From: transfer.stratus.com
X-Received-By OS/2 SMTP Daemon v0.1ß/gigo
Received: gigo.com Sun Aug 27 04:00:57 1995
Received: from light.jjm.com (light.hqsl.stratus.com [134.111.105.15]) by
transfer.stratus.com (8.6.11/8.6.11) with ESMTP id HAA24529 for
<[e-mail]>; Sun, 27 Aug 1995 07:10:52 -0400
Received: from jjmhome.jjm.com ([e-mail] [198.114.254.1]) by
light.jjm.com (8.6.12/8.6.12) with ESMTP id HAA27379 for <[e-mail]>;
Sun, 27 Aug 1995 07:10:51 -0400
Received: from bdragon.UUCP (uucp@localhost) by jjmhome.jjm.com (8.6.12/8.6.12)
with UUCP id HAA21047 for [e-mail]; Sun, 27 Aug 1995 07:09:58 -0400
Received: by bdragon.jjm.com (0.99.950801)
  id AA05915; 18 Aug 95 01:04:47 -0500
From: [e-mail] (Stephen Griffin)
Date: 18 Aug 95 00:46:40 -0400
Subject: Digest doc's
Message-Id: <[e-mail]>
Organization: Black Dragon Inn
To: [e-mail]


--- GIGO+ sn 1 at gigo vsn 0.99.950801
VIA GIGO 1:203/2, Sun Aug 27 1995  at 12:01 UTC